Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 685c471572a3429ea1d2270e071c22c9c36c10734e4d89b8fccc01ead81be04e

Tx prefix hash: 4fb1976d68459bc78cfe7c37de9c2e70ec6af3bfc1f5fddbeb524d66af4705f6
Tx public key: 6fccdb91a282e9ddba03f537ae11d9c334f1903ddd09714de17fd24f69d35e1b
Timestamp: 1631802221 Timestamp [UCT]: 2021-09-16 14:23:41 Age [y:d:h:m:s]: 03:105:02:32:24
Block: 334965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 850890 RingCT/type: yes/0
Extra: 016fccdb91a282e9ddba03f537ae11d9c334f1903ddd09714de17fd24f69d35e1b02110000002afdc024ec000000000000000000

1 output(s) for total of 47.656521953000 dcy

stealth address amount amount idx
00: a3dc8aacb1d86ed1af7a9e114f0d19d2099c55e7c086c3e8a3013e24219cb983 47.656521953000 690634 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": 334975, "vin": [ { "gen": { "height": 334965 } } ], "vout": [ { "amount": 47656521953, "target": { "key": "a3dc8aacb1d86ed1af7a9e114f0d19d2099c55e7c086c3e8a3013e24219cb983" } } ], "extra": [ 1, 111, 204, 219, 145, 162, 130, 233, 221, 186, 3, 245, 55, 174, 17, 217, 195, 52, 241, 144, 61, 221, 9, 113, 77, 225, 127, 210, 79, 105, 211, 94, 27, 2, 17, 0, 0, 0, 42, 253, 192, 36, 236, 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