Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db02c1aeec8740b7adc922a8215d0affe1aeb105ff07b6f4741e7914746747a0

Tx prefix hash: 570358870d57f5fd88f83de4d5d399ba688730af485dd9d84de3e51263519765
Tx public key: 1dd14b03f20999added60c32f9901ad1e344aca4af7a29ab518d3fc23c2c27d1
Timestamp: 1699868382 Timestamp [UCT]: 2023-11-13 09:39:42 Age [y:d:h:m:s]: 01:103:09:40:49
Block: 890662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335039 RingCT/type: yes/0
Extra: 011dd14b03f20999added60c32f9901ad1e344aca4af7a29ab518d3fc23c2c27d102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.686858156000 dcy

stealth address amount amount idx
00: c5a2b2d5ba6fe50540142d59337dc24d8ff62856a1a35e2b1e1e6940ad043d10 0.686858156000 1346691 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": 890672, "vin": [ { "gen": { "height": 890662 } } ], "vout": [ { "amount": 686858156, "target": { "key": "c5a2b2d5ba6fe50540142d59337dc24d8ff62856a1a35e2b1e1e6940ad043d10" } } ], "extra": [ 1, 29, 209, 75, 3, 242, 9, 153, 173, 222, 214, 12, 50, 249, 144, 26, 209, 227, 68, 172, 164, 175, 122, 41, 171, 81, 141, 63, 194, 60, 44, 39, 209, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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