Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33a82925b3fb7ae498ef4a4aa6d19bf568d3be96aa7e301f16ac1622721cfb49

Tx prefix hash: a5bcbaa10b5b6ab336ede7c1816659cf16a61d314ed01ecce4b1a13f95eb674f
Tx public key: 505918c5885ad762fdf5fea98e92e9c3894a26bd6ad153052fb48ef1e458ebbe
Timestamp: 1737062312 Timestamp [UCT]: 2025-01-16 21:18:32 Age [y:d:h:m:s]: 00:056:18:43:42
Block: 1198854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40378 RingCT/type: yes/0
Extra: 01505918c5885ad762fdf5fea98e92e9c3894a26bd6ad153052fb48ef1e458ebbe0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b215817fcb8016c92b38025f5e3d5949452c661bb5c0bf358e1f034d3a705eda 0.600000000000 1685481 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": 1198864, "vin": [ { "gen": { "height": 1198854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b215817fcb8016c92b38025f5e3d5949452c661bb5c0bf358e1f034d3a705eda" } } ], "extra": [ 1, 80, 89, 24, 197, 136, 90, 215, 98, 253, 245, 254, 169, 142, 146, 233, 195, 137, 74, 38, 189, 106, 209, 83, 5, 47, 180, 142, 241, 228, 88, 235, 190, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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