Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a80fec5671570626b8e93f5d8d2d0c4c8409afcbc4d4031ce45b6464269f1be1

Tx prefix hash: 293dd892b3ff915b7d43b838480380cc8a9c51f4f08c1c8ef04210c187220d3d
Tx public key: c7e87b12ae3442f880bea3ff72d3d9e879cd45b501642dc2e8a1068144822f3d
Timestamp: 1751607367 Timestamp [UCT]: 2025-07-04 05:36:07 Age [y:d:h:m:s]: 00:136:21:31:14
Block: 1318415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96115 RingCT/type: yes/0
Extra: 01c7e87b12ae3442f880bea3ff72d3d9e879cd45b501642dc2e8a1068144822f3d02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 616fc7d5cbf9e43ed55977a8ca1fad62d574002c3c6e2979f70e356625d7a40b 0.600000000000 1806094 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": 1318425, "vin": [ { "gen": { "height": 1318415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "616fc7d5cbf9e43ed55977a8ca1fad62d574002c3c6e2979f70e356625d7a40b" } } ], "extra": [ 1, 199, 232, 123, 18, 174, 52, 66, 248, 128, 190, 163, 255, 114, 211, 217, 232, 121, 205, 69, 181, 1, 100, 45, 194, 232, 161, 6, 129, 68, 130, 47, 61, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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