Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539b486837ec5c2dd4a2795840e6c41a84e8ee1379d912bf2fd72da958f6b3b5

Tx prefix hash: cc0575dbc4106622ffac45e9e1f6c5bfdc21353a5560fffef85d70bfa82ae469
Tx public key: 5a256d63ba887c35c6f1ff04c8f71d485864bf3b23675cd19a4d9fa9ba471a53
Timestamp: 1713759007 Timestamp [UCT]: 2024-04-22 04:10:07 Age [y:d:h:m:s]: 01:033:06:41:19
Block: 1005806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284759 RingCT/type: yes/0
Extra: 015a256d63ba887c35c6f1ff04c8f71d485864bf3b23675cd19a4d9fa9ba471a530211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f16e561a09572bc8102fd6d198e90c9ba368102a6c3e23f2d0c695811629355 0.600000000000 1466616 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": 1005816, "vin": [ { "gen": { "height": 1005806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f16e561a09572bc8102fd6d198e90c9ba368102a6c3e23f2d0c695811629355" } } ], "extra": [ 1, 90, 37, 109, 99, 186, 136, 124, 53, 198, 241, 255, 4, 200, 247, 29, 72, 88, 100, 191, 59, 35, 103, 92, 209, 154, 77, 159, 169, 186, 71, 26, 83, 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