Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b982bf41df547c006c812253d509ee76508d90bf4fa497368118328e53c5d984

Tx prefix hash: 0dadd285e7731d88a4011d1a59a3b2c06ee0ecad0bcf51eb8dfcc68fe98395c3
Tx public key: b762563206e925e0e5fad5438b2d91ea43e05fbea83cab1e6e8cce58203fc5b9
Timestamp: 1718315828 Timestamp [UCT]: 2024-06-13 21:57:08 Age [y:d:h:m:s]: 01:002:00:51:39
Block: 1043600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262235 RingCT/type: yes/0
Extra: 01b762563206e925e0e5fad5438b2d91ea43e05fbea83cab1e6e8cce58203fc5b902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79c48e306f524e320019009e1e44c4dde819f96ee05930be4d75c56ad66f34aa 0.600000000000 1512757 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": 1043610, "vin": [ { "gen": { "height": 1043600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79c48e306f524e320019009e1e44c4dde819f96ee05930be4d75c56ad66f34aa" } } ], "extra": [ 1, 183, 98, 86, 50, 6, 233, 37, 224, 229, 250, 213, 67, 139, 45, 145, 234, 67, 224, 95, 190, 168, 60, 171, 30, 110, 140, 206, 88, 32, 63, 197, 185, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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