Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d15b679aa027637f3d574f9e8167f067fb69f5604bad3b2b6100be86c8532976

Tx prefix hash: 894eb4aef8e3d64f28aa8365261ccfa0749fee9537192cb8d6411cf38015bf2e
Tx public key: 509ba3ed8c3a7ae846f7235836cfaf214b05100c97d46f2780f37e5c852f616c
Timestamp: 1766096056 Timestamp [UCT]: 2025-12-18 22:14:16 Age [y:d:h:m:s]: 00:003:10:45:32
Block: 1436572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2467 RingCT/type: yes/0
Extra: 01509ba3ed8c3a7ae846f7235836cfaf214b05100c97d46f2780f37e5c852f616c021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 475ae36ee1116764ed29346ae3bd7a4bc9fa12d1cf4de3358b523030345be606 0.600000000000 1925377 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": 1436582, "vin": [ { "gen": { "height": 1436572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "475ae36ee1116764ed29346ae3bd7a4bc9fa12d1cf4de3358b523030345be606" } } ], "extra": [ 1, 80, 155, 163, 237, 140, 58, 122, 232, 70, 247, 35, 88, 54, 207, 175, 33, 75, 5, 16, 12, 151, 212, 111, 39, 128, 243, 126, 92, 133, 47, 97, 108, 2, 17, 0, 0, 0, 6, 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