Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476ff67674c95cf263232b6f6b6a6e28c670c8b6d234729ed661688523644a2e

Tx prefix hash: 054c4061c1baf4c3caea6883d7318475a3ce20b096ac220f9c6033983162fb48
Tx public key: 2a1b9fb8740d44ed4bd227a8e234092e1ecf7b660350631ed4499fe071ebcbe6
Timestamp: 1581798553 Timestamp [UCT]: 2020-02-15 20:29:13 Age [y:d:h:m:s]: 05:107:18:32:45
Block: 65563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1230142 RingCT/type: yes/0
Extra: 012a1b9fb8740d44ed4bd227a8e234092e1ecf7b660350631ed4499fe071ebcbe6021100000006d81c26c0000000000000000000

1 output(s) for total of 372.188863926000 dcy

stealth address amount amount idx
00: 4f8c35a8de4b46b381c04a6f1fae0c2e9f10e0af35fcf4a835940babe0d1a098 372.188863926000 120980 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": 65573, "vin": [ { "gen": { "height": 65563 } } ], "vout": [ { "amount": 372188863926, "target": { "key": "4f8c35a8de4b46b381c04a6f1fae0c2e9f10e0af35fcf4a835940babe0d1a098" } } ], "extra": [ 1, 42, 27, 159, 184, 116, 13, 68, 237, 75, 210, 39, 168, 226, 52, 9, 46, 30, 207, 123, 102, 3, 80, 99, 30, 212, 73, 159, 224, 113, 235, 203, 230, 2, 17, 0, 0, 0, 6, 216, 28, 38, 192, 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