Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ccf7dda3532278b5325adff0c68d27e4de805f4281b9f32bdd55a6bbbbfb01c

Tx prefix hash: d7d069ff09579399ddd2d7fac4846f5a35f9e44bdb107f8a768dbf15362d4239
Tx public key: ffa3122e4d1e0a349c6dfc63c655644a2fd44abc2475a7460cd9285f05bb21a4
Timestamp: 1762486734 Timestamp [UCT]: 2025-11-07 03:38:54 Age [y:d:h:m:s]: 00:057:04:40:33
Block: 1406658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40967 RingCT/type: yes/0
Extra: 01ffa3122e4d1e0a349c6dfc63c655644a2fd44abc2475a7460cd9285f05bb21a402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131e8620a43d8777a3dfcd27d3e23571f6193c7d2f7c5866f274ab4a1e4f2a69 0.600000000000 1895047 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": 1406668, "vin": [ { "gen": { "height": 1406658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131e8620a43d8777a3dfcd27d3e23571f6193c7d2f7c5866f274ab4a1e4f2a69" } } ], "extra": [ 1, 255, 163, 18, 46, 77, 30, 10, 52, 156, 109, 252, 99, 198, 85, 100, 74, 47, 212, 74, 188, 36, 117, 167, 70, 12, 217, 40, 95, 5, 187, 33, 164, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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