Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4ef66c680c665810a85302121caf0b0fab0e04323a3690a7572dc96dd399130

Tx prefix hash: 998e2e4b24136fe9eb035ba32264c8e2e513c0e05e252363c8a5c618b2db2725
Tx public key: f98ebda07e9fb2313197a21b2be80f70c12774b3e0f13ffb83462d0167aedd8b
Timestamp: 1738521300 Timestamp [UCT]: 2025-02-02 18:35:00 Age [y:d:h:m:s]: 00:279:22:29:57
Block: 1210667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197836 RingCT/type: yes/0
Extra: 01f98ebda07e9fb2313197a21b2be80f70c12774b3e0f13ffb83462d0167aedd8b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8248b8505795adc6bc6bea518822bb5ef2383e1b3fe0d91bcf874804912e523e 0.600000000000 1697420 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": 1210677, "vin": [ { "gen": { "height": 1210667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8248b8505795adc6bc6bea518822bb5ef2383e1b3fe0d91bcf874804912e523e" } } ], "extra": [ 1, 249, 142, 189, 160, 126, 159, 178, 49, 49, 151, 162, 27, 43, 232, 15, 112, 193, 39, 116, 179, 224, 241, 63, 251, 131, 70, 45, 1, 103, 174, 221, 139, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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