Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ccc568529d5e0c23611870489191c34af81097ab41373bf7c64ba4c6be2cacf

Tx prefix hash: e34c6c15db08a6e5e487149cb3a801b7c80327e85c49ac6710117c3d877eba48
Tx public key: c4162c682ce9084ed0ef38511e553e7a85c6a6e3fc810c9020aa26f094814798
Timestamp: 1735830479 Timestamp [UCT]: 2025-01-02 15:07:59 Age [y:d:h:m:s]: 00:069:10:35:43
Block: 1188668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49416 RingCT/type: yes/0
Extra: 01c4162c682ce9084ed0ef38511e553e7a85c6a6e3fc810c9020aa26f0948147980211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4fe9c54a21a8ddef1d8923534bd03fdf5cfe5ea8285e15c49e41f9aa9864b9a 0.600000000000 1675171 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": 1188678, "vin": [ { "gen": { "height": 1188668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4fe9c54a21a8ddef1d8923534bd03fdf5cfe5ea8285e15c49e41f9aa9864b9a" } } ], "extra": [ 1, 196, 22, 44, 104, 44, 233, 8, 78, 208, 239, 56, 81, 30, 85, 62, 122, 133, 198, 166, 227, 252, 129, 12, 144, 32, 170, 38, 240, 148, 129, 71, 152, 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