Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0585e96f3810b42f88e71d91b97f2815a23548d223ecb3e19cd6e5b5c5ae487e

Tx prefix hash: 7be9295a4823b516959442a53dd5a54cf040a235fb27f06a989b5c4bfd4cf873
Tx public key: 178d66c16257f09136ec3fb525fd242ce51be9844a7d356d06ecce18ba78f780
Timestamp: 1701728106 Timestamp [UCT]: 2023-12-04 22:15:06 Age [y:d:h:m:s]: 01:121:07:52:07
Block: 906071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347863 RingCT/type: yes/0
Extra: 01178d66c16257f09136ec3fb525fd242ce51be9844a7d356d06ecce18ba78f78002110000000633af99f4000000000000000000

1 output(s) for total of 0.610675678000 dcy

stealth address amount amount idx
00: 86b33f38e79c17bc0933c1c2d88c7692258dcd2933524485eebf2cb1a951655d 0.610675678000 1362992 of 0

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": 906081, "vin": [ { "gen": { "height": 906071 } } ], "vout": [ { "amount": 610675678, "target": { "key": "86b33f38e79c17bc0933c1c2d88c7692258dcd2933524485eebf2cb1a951655d" } } ], "extra": [ 1, 23, 141, 102, 193, 98, 87, 240, 145, 54, 236, 63, 181, 37, 253, 36, 44, 229, 27, 233, 132, 74, 125, 53, 109, 6, 236, 206, 24, 186, 120, 247, 128, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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