Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a6f18162e540cb8226ec20d30f2dbd5bf706892d7e99722fd360902a55019cf

Tx prefix hash: 3f6e1bb7956b1103599cbd8010a342940ac8c697bd6ace14ac7f68f4c96ec624
Tx public key: 3f33bef71167479983488a0e0705a7ec2ca2b9cfe8ecfae094f418bdab349c61
Timestamp: 1755877970 Timestamp [UCT]: 2025-08-22 15:52:50 Age [y:d:h:m:s]: 00:088:22:15:43
Block: 1352074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63497 RingCT/type: yes/0
Extra: 013f33bef71167479983488a0e0705a7ec2ca2b9cfe8ecfae094f418bdab349c610211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b525e8e8d527b0d819db49baa28acd324e0ef3858fef8cb7540d979f0051b85e 0.600000000000 1840035 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": 1352084, "vin": [ { "gen": { "height": 1352074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b525e8e8d527b0d819db49baa28acd324e0ef3858fef8cb7540d979f0051b85e" } } ], "extra": [ 1, 63, 51, 190, 247, 17, 103, 71, 153, 131, 72, 138, 14, 7, 5, 167, 236, 44, 162, 185, 207, 232, 236, 250, 224, 148, 244, 24, 189, 171, 52, 156, 97, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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