Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d9c16190dfcf947e67e6777eb3463825f2d13bdbee974eb0e09bb3cb74fa5bc

Tx prefix hash: 2f0ad06575d4ca177ab62491c4cff18845175eb19f84b1b1f84d69acf4afac96
Tx public key: 8584c23ce918d9bd3108dd7f44a3e05bc93f9d9921d87a115dd12bf300179d8f
Timestamp: 1579145484 Timestamp [UCT]: 2020-01-16 03:31:24 Age [y:d:h:m:s]: 04:319:06:01:46
Block: 46499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117678 RingCT/type: yes/0
Extra: 018584c23ce918d9bd3108dd7f44a3e05bc93f9d9921d87a115dd12bf300179d8f021100000058b221b3d1000000000000000000

1 output(s) for total of 430.464998773000 dcy

stealth address amount amount idx
00: 616049e3cd4d9d6a69e671267d6b527d48d0fc79fa20ee10107993f70b90ed36 430.464998773000 85566 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": 46509, "vin": [ { "gen": { "height": 46499 } } ], "vout": [ { "amount": 430464998773, "target": { "key": "616049e3cd4d9d6a69e671267d6b527d48d0fc79fa20ee10107993f70b90ed36" } } ], "extra": [ 1, 133, 132, 194, 60, 233, 24, 217, 189, 49, 8, 221, 127, 68, 163, 224, 91, 201, 63, 157, 153, 33, 216, 122, 17, 93, 209, 43, 243, 0, 23, 157, 143, 2, 17, 0, 0, 0, 88, 178, 33, 179, 209, 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