Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c15af7aef61b53ba6a07be8329eed017b3fcddc881c315b906cf2379f612d1bf

Tx prefix hash: 416a58cf3c41c05846a42489c162ef093c6a6c2af4d85112fcfd2337696da4cd
Tx public key: 195934e21bdc3505f6a9608993ad2c08f6a3d0f861f7602c06241019a0a41281
Timestamp: 1732325407 Timestamp [UCT]: 2024-11-23 01:30:07 Age [y:d:h:m:s]: 00:000:20:17:50
Block: 1159647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594 RingCT/type: yes/0
Extra: 01195934e21bdc3505f6a9608993ad2c08f6a3d0f861f7602c06241019a0a4128102110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc09c4db5d3e56527185ca3ae581d2d0788208ce3c5302e2a9e56682464f9e54 0.600000000000 1645286 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": 1159657, "vin": [ { "gen": { "height": 1159647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc09c4db5d3e56527185ca3ae581d2d0788208ce3c5302e2a9e56682464f9e54" } } ], "extra": [ 1, 25, 89, 52, 226, 27, 220, 53, 5, 246, 169, 96, 137, 147, 173, 44, 8, 246, 163, 208, 248, 97, 247, 96, 44, 6, 36, 16, 25, 160, 164, 18, 129, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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