Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344f23b2f8508014af1fc192511d78fb18277442d74b43ccf97176613282fc2d

Tx prefix hash: 3e4359eacccdb2977e41b9e86e228f8fafa0a226fa686408f7a8ef3880799f54
Tx public key: dc02dcd930796a21293c8caf512570a3b609d7089785e1e591cab4071f1a0e3d
Timestamp: 1708256667 Timestamp [UCT]: 2024-02-18 11:44:27 Age [y:d:h:m:s]: 01:036:04:53:32
Block: 960199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286889 RingCT/type: yes/0
Extra: 01dc02dcd930796a21293c8caf512570a3b609d7089785e1e591cab4071f1a0e3d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65cdd0a997385ea208b6adb2ca4c1c580ec2c8413bad1a134bc23cd8297d25e8 0.600000000000 1419760 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": 960209, "vin": [ { "gen": { "height": 960199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65cdd0a997385ea208b6adb2ca4c1c580ec2c8413bad1a134bc23cd8297d25e8" } } ], "extra": [ 1, 220, 2, 220, 217, 48, 121, 106, 33, 41, 60, 140, 175, 81, 37, 112, 163, 182, 9, 215, 8, 151, 133, 225, 229, 145, 202, 180, 7, 31, 26, 14, 61, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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