Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5df18741104049941ca0916294fecfc0fcefb3ffb62e2a22e8a74e7de9172f62

Tx prefix hash: 2f7cc6647fd0c3cfae4d5fce0d11d4eb3daa5a08f1070b1f2823e10f1d67b1be
Tx public key: 1b6ade5263eadfec383711589a428a8653ee4acbffcb367a36ddd1f0b3fb5af1
Timestamp: 1763548625 Timestamp [UCT]: 2025-11-19 10:37:05 Age [y:d:h:m:s]: 00:008:19:49:17
Block: 1415470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6317 RingCT/type: yes/0
Extra: 011b6ade5263eadfec383711589a428a8653ee4acbffcb367a36ddd1f0b3fb5af1021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 675740656bd846c205e69f4bc849783e9a9e046d9b49f3c6be015646540a1572 0.600000000000 1903971 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": 1415480, "vin": [ { "gen": { "height": 1415470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "675740656bd846c205e69f4bc849783e9a9e046d9b49f3c6be015646540a1572" } } ], "extra": [ 1, 27, 106, 222, 82, 99, 234, 223, 236, 56, 55, 17, 88, 154, 66, 138, 134, 83, 238, 74, 203, 255, 203, 54, 122, 54, 221, 209, 240, 179, 251, 90, 241, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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