Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e30baf8198db9057be1d6e8d77a19549e2eeed7315356ac028830067bc6f0d

Tx prefix hash: 711acd690c7bb1132d8d4d09ee7193f6269c3665734b271c71f3eac6fca27b2c
Tx public key: df0b196c0d1dd92f2a26079d1107e55ece2ec2ac4161ab0ab4a764ae39170f2c
Timestamp: 1620778386 Timestamp [UCT]: 2021-05-12 00:13:06 Age [y:d:h:m:s]: 03:268:06:02:51
Block: 259191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 951820 RingCT/type: yes/0
Extra: 01df0b196c0d1dd92f2a26079d1107e55ece2ec2ac4161ab0ab4a764ae39170f2c02110000002c1b9dd99a000000000000000000

1 output(s) for total of 84.955826776000 dcy

stealth address amount amount idx
00: 5eabf152e74f0f03274ae269a911fe6dc6f0fa8b758fadffc0c7c11f1018a3dd 84.955826776000 546006 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": 259201, "vin": [ { "gen": { "height": 259191 } } ], "vout": [ { "amount": 84955826776, "target": { "key": "5eabf152e74f0f03274ae269a911fe6dc6f0fa8b758fadffc0c7c11f1018a3dd" } } ], "extra": [ 1, 223, 11, 25, 108, 13, 29, 217, 47, 42, 38, 7, 157, 17, 7, 229, 94, 206, 46, 194, 172, 65, 97, 171, 10, 180, 167, 100, 174, 57, 23, 15, 44, 2, 17, 0, 0, 0, 44, 27, 157, 217, 154, 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