Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54c6a467d90a3fbc70466a776c9eee87f919b781df0f54cf1ee61925f4d9109d

Tx prefix hash: 48dcc49771f7936e7d7e7e7d99480155c0f41b5e3db750d32c1c4883810e91a1
Tx public key: 45c7492598a9acef4b1e163b011ee9a548b16bc6864be9a6bcd82573eef1114f
Timestamp: 1649507223 Timestamp [UCT]: 2022-04-09 12:27:03 Age [y:d:h:m:s]: 02:235:00:45:49
Block: 476543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687753 RingCT/type: yes/0
Extra: 0145c7492598a9acef4b1e163b011ee9a548b16bc6864be9a6bcd82573eef1114f0211000000092e6b1fd5000000000000000000

1 output(s) for total of 16.181376333000 dcy

stealth address amount amount idx
00: 1760310e17129f29053fd6313e3875471a25c5e2b4bddae4b68091ad3c6e4cc4 16.181376333000 897034 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": 476553, "vin": [ { "gen": { "height": 476543 } } ], "vout": [ { "amount": 16181376333, "target": { "key": "1760310e17129f29053fd6313e3875471a25c5e2b4bddae4b68091ad3c6e4cc4" } } ], "extra": [ 1, 69, 199, 73, 37, 152, 169, 172, 239, 75, 30, 22, 59, 1, 30, 233, 165, 72, 177, 107, 198, 134, 75, 233, 166, 188, 216, 37, 115, 238, 241, 17, 79, 2, 17, 0, 0, 0, 9, 46, 107, 31, 213, 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