Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51101ca0b6b1c54c0dc168ef80c02364c571de061a164496f9a4954190ad468d

Tx prefix hash: c9dcf526b19a885d50fe55d23ea29c130eea460c7d580510a89687d0388bf997
Tx public key: e0a35df279d3b87b3f5d0a33056a5f95f993467a6df5ed2a2c36bcae6739b8f6
Timestamp: 1578450731 Timestamp [UCT]: 2020-01-08 02:32:11 Age [y:d:h:m:s]: 04:327:20:23:36
Block: 40924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123651 RingCT/type: yes/0
Extra: 01e0a35df279d3b87b3f5d0a33056a5f95f993467a6df5ed2a2c36bcae6739b8f60211000000022264afe6000000000000000000

1 output(s) for total of 449.171366594000 dcy

stealth address amount amount idx
00: 40be84f7749a21883cfd6374cae21fa83f26c902e5a73c9d861f0e12d68c1ea3 449.171366594000 72390 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": 40934, "vin": [ { "gen": { "height": 40924 } } ], "vout": [ { "amount": 449171366594, "target": { "key": "40be84f7749a21883cfd6374cae21fa83f26c902e5a73c9d861f0e12d68c1ea3" } } ], "extra": [ 1, 224, 163, 93, 242, 121, 211, 184, 123, 63, 93, 10, 51, 5, 106, 95, 149, 249, 147, 70, 122, 109, 245, 237, 42, 44, 54, 188, 174, 103, 57, 184, 246, 2, 17, 0, 0, 0, 2, 34, 100, 175, 230, 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