Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22e518a4b49de543d36784b717b6284b772d9f7d2aa3e23f54baaadb0131c468

Tx prefix hash: 25f0564cb82bf6d9ebea80dedfc50c005e86a272c0424a50c3d8423bcc5ccb3b
Tx public key: 2b2b564caa27a1c4b181862535c55e21e1fc804e1d7b997d79a28605e1220bb0
Timestamp: 1736003108 Timestamp [UCT]: 2025-01-04 15:05:08 Age [y:d:h:m:s]: 00:351:19:20:53
Block: 1190106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248981 RingCT/type: yes/0
Extra: 012b2b564caa27a1c4b181862535c55e21e1fc804e1d7b997d79a28605e1220bb002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92a3720eeb99ef0d8eeb29fbc6e803fd67e6e7843c419ee448922b36c94e58d7 0.600000000000 1676621 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": 1190116, "vin": [ { "gen": { "height": 1190106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92a3720eeb99ef0d8eeb29fbc6e803fd67e6e7843c419ee448922b36c94e58d7" } } ], "extra": [ 1, 43, 43, 86, 76, 170, 39, 161, 196, 177, 129, 134, 37, 53, 197, 94, 33, 225, 252, 128, 78, 29, 123, 153, 125, 121, 162, 134, 5, 225, 34, 11, 176, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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