Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97933973573337d72b768dbb7ce6a33e181bf7f3c159e1c1e21d3175dfc0b993

Tx prefix hash: a5002173c5aff7325407686f5e00b186bed7b3f990eb70c3c110165f95c53f57
Tx public key: a7f378bc18f792f63b51371bb98a4ad5cbb1c769c4a1b383d861c854ce109eed
Timestamp: 1577155110 Timestamp [UCT]: 2019-12-24 02:38:30 Age [y:d:h:m:s]: 05:080:14:29:48
Block: 30279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207544 RingCT/type: yes/0
Extra: 01a7f378bc18f792f63b51371bb98a4ad5cbb1c769c4a1b383d861c854ce109eed0211000000024ac5aa02000000000000000000

1 output(s) for total of 487.203598961000 dcy

stealth address amount amount idx
00: 7214b4a50f9faa6a056f66afe39491f358b5413d7efd1a05cde8deeee47048d1 487.203598961000 49993 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": 30289, "vin": [ { "gen": { "height": 30279 } } ], "vout": [ { "amount": 487203598961, "target": { "key": "7214b4a50f9faa6a056f66afe39491f358b5413d7efd1a05cde8deeee47048d1" } } ], "extra": [ 1, 167, 243, 120, 188, 24, 247, 146, 246, 59, 81, 55, 27, 185, 138, 74, 213, 203, 177, 199, 105, 196, 161, 179, 131, 216, 97, 200, 84, 206, 16, 158, 237, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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