Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5c60006c3b3843777b7ae4ba6d443be507e4f55f71a7ef2d9207cc6030119f5

Tx prefix hash: 61a9367849b79b9856e0aa954d3d8defe15c1cdf316412104793c86dd0075cf0
Tx public key: e4aee60b1882e824c23680603e4a01a75a814a264132dacae8bcf910e8dafb43
Timestamp: 1742010279 Timestamp [UCT]: 2025-03-15 03:44:39 Age [y:d:h:m:s]: 00:321:00:58:57
Block: 1239569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227100 RingCT/type: yes/0
Extra: 01e4aee60b1882e824c23680603e4a01a75a814a264132dacae8bcf910e8dafb43021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38e8eeaa0a3f81ecb53e9496999b73fba4788d782b9b6bc8a8444a8d7e6369ef 0.600000000000 1726534 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": 1239579, "vin": [ { "gen": { "height": 1239569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38e8eeaa0a3f81ecb53e9496999b73fba4788d782b9b6bc8a8444a8d7e6369ef" } } ], "extra": [ 1, 228, 174, 230, 11, 24, 130, 232, 36, 194, 54, 128, 96, 62, 74, 1, 167, 90, 129, 74, 38, 65, 50, 218, 202, 232, 188, 249, 16, 232, 218, 251, 67, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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