Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c7ed31cb13a369d83e908d071aef44c65865e7c30943126292e90961e0b810e

Tx prefix hash: d4530a4228cbcb8a4add7554adf069e1e711e03917ef4220c2d0314b9441f467
Tx public key: 218626432ccad93e5e8a613b966f1eb7fc4fb558a42f9550f959a6e639bb469d
Timestamp: 1732390175 Timestamp [UCT]: 2024-11-23 19:29:35 Age [y:d:h:m:s]: 00:155:19:46:42
Block: 1160174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111207 RingCT/type: yes/0
Extra: 01218626432ccad93e5e8a613b966f1eb7fc4fb558a42f9550f959a6e639bb469d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd5f7360d0abe6027dae59432c9a0879129aa55a35dec40c23d8a2c350312517 0.600000000000 1645817 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": 1160184, "vin": [ { "gen": { "height": 1160174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd5f7360d0abe6027dae59432c9a0879129aa55a35dec40c23d8a2c350312517" } } ], "extra": [ 1, 33, 134, 38, 67, 44, 202, 217, 62, 94, 138, 97, 59, 150, 111, 30, 183, 252, 79, 181, 88, 164, 47, 149, 80, 249, 89, 166, 230, 57, 187, 70, 157, 2, 17, 0, 0, 0, 1, 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