Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4938bc0b20024d17f42542d3ed2eed1839625265ce8fffbdb63737077f4b8ed

Tx prefix hash: d1310c8425f6d69b4ebc07e864187ed7228a62d719eea3b84fe31b5473002a7d
Tx public key: d1f570c60f494d4baca6f977676415d1bbf4d8199d9e8f62692523d88d41ff37
Timestamp: 1722785854 Timestamp [UCT]: 2024-08-04 15:37:34 Age [y:d:h:m:s]: 00:224:20:51:17
Block: 1080648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160621 RingCT/type: yes/0
Extra: 01d1f570c60f494d4baca6f977676415d1bbf4d8199d9e8f62692523d88d41ff3702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fa84f9c64b57167f2e98e8350f98fc2cd5fb711b30b2d3ee6d38b60651c0a0c 0.600000000000 1554089 of 15

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": 1080658, "vin": [ { "gen": { "height": 1080648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa84f9c64b57167f2e98e8350f98fc2cd5fb711b30b2d3ee6d38b60651c0a0c" } } ], "extra": [ 1, 209, 245, 112, 198, 15, 73, 77, 75, 172, 166, 249, 119, 103, 100, 21, 209, 187, 244, 216, 25, 157, 158, 143, 98, 105, 37, 35, 216, 141, 65, 255, 55, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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