Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f00ef2b443a5b4fba10f9c646778039cbc4f61025b9e4eb1b6622a7e6c80cf69

Tx prefix hash: 234d28cd66339412ab8c9ef9ee52f8ca3846aaee72affa73ac6754ccbdbe0ce6
Tx public key: af74787787c4b13ad057f8302b7a537ad1b4aec9dc99c8f2c2f8c31a88f8aee9
Timestamp: 1580110046 Timestamp [UCT]: 2020-01-27 07:27:26 Age [y:d:h:m:s]: 05:282:09:36:28
Block: 53585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1350611 RingCT/type: yes/0
Extra: 01af74787787c4b13ad057f8302b7a537ad1b4aec9dc99c8f2c2f8c31a88f8aee9021100000003ff58ae94000000000000000000

1 output(s) for total of 407.803997408000 dcy

stealth address amount amount idx
00: 8e6cd6456b3fa6c453354efa4b9c867f86dc983722b5b0966a20908786f71a4e 407.803997408000 99385 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": 53595, "vin": [ { "gen": { "height": 53585 } } ], "vout": [ { "amount": 407803997408, "target": { "key": "8e6cd6456b3fa6c453354efa4b9c867f86dc983722b5b0966a20908786f71a4e" } } ], "extra": [ 1, 175, 116, 120, 119, 135, 196, 177, 58, 208, 87, 248, 48, 43, 122, 83, 122, 209, 180, 174, 201, 220, 153, 200, 242, 194, 248, 195, 26, 136, 248, 174, 233, 2, 17, 0, 0, 0, 3, 255, 88, 174, 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