Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e19d178d4c4fd443d5535ef7f9c439e71aa2ac5ceb6c1c96a416a43fae8f1d03

Tx prefix hash: 68a95b377fd8b7edee55d80573c5f1b75849a7d938db7722d4105f3aa1bcc6c0
Tx public key: 814ead20523ade7212b3b149c05ebe7806d8afcc3a73e00c919c7f7651408851
Timestamp: 1745690497 Timestamp [UCT]: 2025-04-26 18:01:37 Age [y:d:h:m:s]: 00:204:12:15:33
Block: 1270037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143868 RingCT/type: yes/0
Extra: 01814ead20523ade7212b3b149c05ebe7806d8afcc3a73e00c919c7f76514088510211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 137ef8b6c0c6a5481759abed333049c593d6c9dcaf029c133476b0e7d76aeea8 0.600000000000 1757278 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": 1270047, "vin": [ { "gen": { "height": 1270037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "137ef8b6c0c6a5481759abed333049c593d6c9dcaf029c133476b0e7d76aeea8" } } ], "extra": [ 1, 129, 78, 173, 32, 82, 58, 222, 114, 18, 179, 177, 73, 192, 94, 190, 120, 6, 216, 175, 204, 58, 115, 224, 12, 145, 156, 127, 118, 81, 64, 136, 81, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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