Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c32bd1766652c98328b95b05b2af8dbe79df31439d76cdb24e2ed8d46196bba

Tx prefix hash: 307624789f654289cfa5f89562d852b60ab13ee1606ca4684d232424ed234f29
Tx public key: 1ff675315a0275ca4a0d59049df15d3e532b833c330d07d46a57047597b9dcd2
Timestamp: 1739048239 Timestamp [UCT]: 2025-02-08 20:57:19 Age [y:d:h:m:s]: 00:349:19:53:53
Block: 1215042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247687 RingCT/type: yes/0
Extra: 011ff675315a0275ca4a0d59049df15d3e532b833c330d07d46a57047597b9dcd2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2e8eac20dfb4c5322ecb0157b630b9c01b5b7edf80415d2957c667c7188df2b 0.600000000000 1701839 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": 1215052, "vin": [ { "gen": { "height": 1215042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2e8eac20dfb4c5322ecb0157b630b9c01b5b7edf80415d2957c667c7188df2b" } } ], "extra": [ 1, 31, 246, 117, 49, 90, 2, 117, 202, 74, 13, 89, 4, 157, 241, 93, 62, 83, 43, 131, 60, 51, 13, 7, 212, 106, 87, 4, 117, 151, 185, 220, 210, 2, 17, 0, 0, 0, 3, 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