Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eb70f03bd9862eb31d5f24759f21d6b3f641ce1c3fd04d9bb5ef8d92d08fb2c

Tx prefix hash: 38e35854fdacf8a9f7322343396cba2c61c3aae273695fd1f46c3a2d3925bd95
Tx public key: e7d2e011c79c1a883685b042f22124bea54397c73a98c47ef1f4272af7817911
Timestamp: 1734008726 Timestamp [UCT]: 2024-12-12 13:05:26 Age [y:d:h:m:s]: 00:096:22:32:05
Block: 1173605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69069 RingCT/type: yes/0
Extra: 01e7d2e011c79c1a883685b042f22124bea54397c73a98c47ef1f4272af7817911021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f8c154dd08f0bd6081672ef50b09280bbfe88220edf3c5cb1563e6d244cadc7 0.600000000000 1659646 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": 1173615, "vin": [ { "gen": { "height": 1173605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f8c154dd08f0bd6081672ef50b09280bbfe88220edf3c5cb1563e6d244cadc7" } } ], "extra": [ 1, 231, 210, 224, 17, 199, 156, 26, 136, 54, 133, 176, 66, 242, 33, 36, 190, 165, 67, 151, 199, 58, 152, 196, 126, 241, 244, 39, 42, 247, 129, 121, 17, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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