Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d066e47894bf2c3e98536c6792ae42d11e80991e9b93a0c552a2d66c56f908e

Tx prefix hash: dcf998ba3eba44312a8062e9cba09f69e1810dbf6a4493235fbce9b843d1b720
Tx public key: 485e6e5acd96ec7f638718663bf01ea4ba912224adcdb8d8569221dacd81b77d
Timestamp: 1718668701 Timestamp [UCT]: 2024-06-17 23:58:21 Age [y:d:h:m:s]: 00:167:08:02:32
Block: 1046519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119766 RingCT/type: yes/0
Extra: 01485e6e5acd96ec7f638718663bf01ea4ba912224adcdb8d8569221dacd81b77d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cf594a410b69047a72caca9d89bc71fac0a6394c5ff5a57d5e5d371f161244f 0.600000000000 1516334 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": 1046529, "vin": [ { "gen": { "height": 1046519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cf594a410b69047a72caca9d89bc71fac0a6394c5ff5a57d5e5d371f161244f" } } ], "extra": [ 1, 72, 94, 110, 90, 205, 150, 236, 127, 99, 135, 24, 102, 59, 240, 30, 164, 186, 145, 34, 36, 173, 205, 184, 216, 86, 146, 33, 218, 205, 129, 183, 125, 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