Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1370b2efd770156ae6517d0d5cdb8ae518041d12644fe7031095bfa709d8e4aa

Tx prefix hash: 1e28bbc8482fb2d0ff021f210c64a8476ea2c814a83edcced1511e499e9879b5
Tx public key: 744932eff1d84f008b041548bd5cd950b7f5d7dcba6c2a37391dd5e92e219581
Timestamp: 1707707719 Timestamp [UCT]: 2024-02-12 03:15:19 Age [y:d:h:m:s]: 01:133:06:20:41
Block: 955637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356091 RingCT/type: yes/0
Extra: 01744932eff1d84f008b041548bd5cd950b7f5d7dcba6c2a37391dd5e92e2195810211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b39a263b29615cd582ad93950c5ea030f1a713a4b1b7f021529c73582f19993 0.600000000000 1414935 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": 955647, "vin": [ { "gen": { "height": 955637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b39a263b29615cd582ad93950c5ea030f1a713a4b1b7f021529c73582f19993" } } ], "extra": [ 1, 116, 73, 50, 239, 241, 216, 79, 0, 139, 4, 21, 72, 189, 92, 217, 80, 183, 245, 215, 220, 186, 108, 42, 55, 57, 29, 213, 233, 46, 33, 149, 129, 2, 17, 0, 0, 0, 4, 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