Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c956a34f8eb2c0e0a0d8600aa9d6711a4c25254ec739a6885ff85d608ab39c05

Tx prefix hash: e8e6783ef74aac8b9a87c10b8e903c85f239554bdf5dbf181a36d932f16830f1
Tx public key: f147ce7126292b9530ae89d4390cbb073c0729035cc595c931713a4c3aaf8c58
Timestamp: 1764518553 Timestamp [UCT]: 2025-11-30 16:02:33 Age [y:d:h:m:s]: 00:039:03:48:36
Block: 1423507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28048 RingCT/type: yes/0
Extra: 01f147ce7126292b9530ae89d4390cbb073c0729035cc595c931713a4c3aaf8c58021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 533a2e083c532600041575701302e7004ed9e958bc1619d73a94bf91b8966ab2 0.600000000000 1912120 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": 1423517, "vin": [ { "gen": { "height": 1423507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "533a2e083c532600041575701302e7004ed9e958bc1619d73a94bf91b8966ab2" } } ], "extra": [ 1, 241, 71, 206, 113, 38, 41, 43, 149, 48, 174, 137, 212, 57, 12, 187, 7, 60, 7, 41, 3, 92, 197, 149, 201, 49, 113, 58, 76, 58, 175, 140, 88, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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