Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bba43b4d54b1006e81a108474a81c22dbb1200f4b6ff8b33dd65e6b4ce0aad4d

Tx prefix hash: bf00f98816d4d4819da88bc9897d5cb3839ffc67405f67fffcfd7ab3afa2239b
Tx public key: 40346a61d75c7cbbf8db7e57f40a1e35b38d9d88d90e3f4ce0132ff45905f177
Timestamp: 1589540214 Timestamp [UCT]: 2020-05-15 10:56:54 Age [y:d:h:m:s]: 04:228:08:44:06
Block: 100918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1084297 RingCT/type: yes/0
Extra: 0140346a61d75c7cbbf8db7e57f40a1e35b38d9d88d90e3f4ce0132ff45905f17702110000000737fb5df4000000000000000000

1 output(s) for total of 284.200630236000 dcy

stealth address amount amount idx
00: 9b15a3a4b93813ff0efda1c7576c7b452916bf1723c3f72fdef8635761c6afc5 284.200630236000 177730 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 100928, "vin": [ { "gen": { "height": 100918 } } ], "vout": [ { "amount": 284200630236, "target": { "key": "9b15a3a4b93813ff0efda1c7576c7b452916bf1723c3f72fdef8635761c6afc5" } } ], "extra": [ 1, 64, 52, 106, 97, 215, 92, 124, 187, 248, 219, 126, 87, 244, 10, 30, 53, 179, 141, 157, 136, 217, 14, 63, 76, 224, 19, 47, 244, 89, 5, 241, 119, 2, 17, 0, 0, 0, 7, 55, 251, 93, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8