Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d60ab9e82a3ffb7dc1c3235f2579dd09730b8c0fe8105a9f467c52de64f106bd

Tx prefix hash: 292c1c52eeb7a1b091a0b1daca595b04059b96c210c9384089f2e95daa2ae892
Tx public key: 455925635d0780795c43431c75a15f1ed17162b892cca6911d0264a73f1bf7db
Timestamp: 1581946848 Timestamp [UCT]: 2020-02-17 13:40:48 Age [y:d:h:m:s]: 04:316:00:40:45
Block: 66692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118365 RingCT/type: yes/0
Extra: 01455925635d0780795c43431c75a15f1ed17162b892cca6911d0264a73f1bf7db0211000000020aca7173000000000000000000

1 output(s) for total of 368.996738364000 dcy

stealth address amount amount idx
00: 1c90454c2062dd0d6ab3c87c935e8f1282a0dff78285ef61a70ea4db16cae22d 368.996738364000 122855 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": 66702, "vin": [ { "gen": { "height": 66692 } } ], "vout": [ { "amount": 368996738364, "target": { "key": "1c90454c2062dd0d6ab3c87c935e8f1282a0dff78285ef61a70ea4db16cae22d" } } ], "extra": [ 1, 69, 89, 37, 99, 93, 7, 128, 121, 92, 67, 67, 28, 117, 161, 95, 30, 209, 113, 98, 184, 146, 204, 166, 145, 29, 2, 100, 167, 63, 27, 247, 219, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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