Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3e6c4c52fa1421571a0203e5c2da29127653c7e1dea968e7c8ee12be564012

Tx prefix hash: 9c956274896234381375a61c80d6e1ca0223d83f7889d993c7584144e58b7a4a
Tx public key: b7dbee9ba24fce02b9d1112305c7a3ccfb78baaad1ec06d92975a2017b4d5f90
Timestamp: 1711945642 Timestamp [UCT]: 2024-04-01 04:27:22 Age [y:d:h:m:s]: 01:053:19:34:05
Block: 990750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299495 RingCT/type: yes/0
Extra: 01b7dbee9ba24fce02b9d1112305c7a3ccfb78baaad1ec06d92975a2017b4d5f900211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e88f66132f2b17b591a6d3611d6d0efc527b47f93a24fecf7ddf44ff6d270fa 0.600000000000 1451078 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": 990760, "vin": [ { "gen": { "height": 990750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e88f66132f2b17b591a6d3611d6d0efc527b47f93a24fecf7ddf44ff6d270fa" } } ], "extra": [ 1, 183, 219, 238, 155, 162, 79, 206, 2, 185, 209, 17, 35, 5, 199, 163, 204, 251, 120, 186, 170, 209, 236, 6, 217, 41, 117, 162, 1, 123, 77, 95, 144, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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