Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 875c45a89b2db94045c2d13833a12d63c9e1f234c33de2785a3190f75d9f7eb7

Tx prefix hash: 625c1bfcc43a7b42651270895b4b93fffc56bdf02c6c3d393cd47f9e20bba003
Tx public key: 321c906c06bad62224c7d5f9dd54c4dbed3cd1e5fe959065ed47c51dd3fd7dd0
Timestamp: 1718577097 Timestamp [UCT]: 2024-06-16 22:31:37 Age [y:d:h:m:s]: 00:332:02:18:59
Block: 1045773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237336 RingCT/type: yes/0
Extra: 01321c906c06bad62224c7d5f9dd54c4dbed3cd1e5fe959065ed47c51dd3fd7dd00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67b0c7c33b9b183c0583ed240db551567d5ca7ac30151f9a18a259807eb81db2 0.600000000000 1515440 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": 1045783, "vin": [ { "gen": { "height": 1045773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67b0c7c33b9b183c0583ed240db551567d5ca7ac30151f9a18a259807eb81db2" } } ], "extra": [ 1, 50, 28, 144, 108, 6, 186, 214, 34, 36, 199, 213, 249, 221, 84, 196, 219, 237, 60, 209, 229, 254, 149, 144, 101, 237, 71, 197, 29, 211, 253, 125, 208, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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