Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86de028621f9f4065f206b9cf0a864259c5807cf8492cf76490d94b8cdaa187a

Tx prefix hash: d573cbe240b5878381b69a0a9a574960db9e7f96f4948296bba3f5c23edbffa3
Tx public key: b26ee9fff068c2a83c55e066863b00b3e625c05953fdae37ec3dc95f675f4135
Timestamp: 1713131708 Timestamp [UCT]: 2024-04-14 21:55:08 Age [y:d:h:m:s]: 01:206:06:05:08
Block: 1000596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406076 RingCT/type: yes/0
Extra: 01b26ee9fff068c2a83c55e066863b00b3e625c05953fdae37ec3dc95f675f413502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b753b74d1c3828a7c67d53243a9de0033666695013640edde1d5d0cb028731c 0.600000000000 1461094 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": 1000606, "vin": [ { "gen": { "height": 1000596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b753b74d1c3828a7c67d53243a9de0033666695013640edde1d5d0cb028731c" } } ], "extra": [ 1, 178, 110, 233, 255, 240, 104, 194, 168, 60, 85, 224, 102, 134, 59, 0, 179, 230, 37, 192, 89, 83, 253, 174, 55, 236, 61, 201, 95, 103, 95, 65, 53, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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