Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66fce0b93f2b767a9b1888da9937e35e786f0728d641e55b7649edc9aa9a91dd

Tx prefix hash: bb364254d5346e6a72000d7ef744fc45763d24fb53de44f40d763bc1958e33ba
Tx public key: b7b19d491ef7d8a8586de7a8beda0c0084fb6d5e1b3ad5bdfa88b328eb1e873a
Timestamp: 1676606344 Timestamp [UCT]: 2023-02-17 03:59:04 Age [y:d:h:m:s]: 02:262:09:46:35
Block: 698690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706833 RingCT/type: yes/0
Extra: 01b7b19d491ef7d8a8586de7a8beda0c0084fb6d5e1b3ad5bdfa88b328eb1e873a021100000008835e4d22000000000000000000

1 output(s) for total of 2.971323277000 dcy

stealth address amount amount idx
00: 35b8e0b013a3c25b7ba35f0bfecef3169e8e951c4bd2c4643fa87fd9e1c404eb 2.971323277000 1142029 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": 698700, "vin": [ { "gen": { "height": 698690 } } ], "vout": [ { "amount": 2971323277, "target": { "key": "35b8e0b013a3c25b7ba35f0bfecef3169e8e951c4bd2c4643fa87fd9e1c404eb" } } ], "extra": [ 1, 183, 177, 157, 73, 30, 247, 216, 168, 88, 109, 231, 168, 190, 218, 12, 0, 132, 251, 109, 94, 27, 58, 213, 189, 250, 136, 179, 40, 235, 30, 135, 58, 2, 17, 0, 0, 0, 8, 131, 94, 77, 34, 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