Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41ddfe5bab1c41e88811f3848e0e1573a34c0f054cf9a6546de5ab91328c51ce

Tx prefix hash: 19b0d22f1d91021b3534b404e39ce8cc296bd8ec82641ef818345ddd398e0b8d
Tx public key: 20485aa5b128b60e9e69cd33cc291e8eb2d58518d8de7a0af76f85eb2ef8ad68
Timestamp: 1694030182 Timestamp [UCT]: 2023-09-06 19:56:22 Age [y:d:h:m:s]: 01:223:00:35:28
Block: 842437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420508 RingCT/type: yes/0
Extra: 0120485aa5b128b60e9e69cd33cc291e8eb2d58518d8de7a0af76f85eb2ef8ad680211000000014b8f5122000000000000000000

1 output(s) for total of 0.992331036000 dcy

stealth address amount amount idx
00: a4a61d97dcce7122955eb8ca89aab1d5186a85e12797bc383abfc0ff0cb8babe 0.992331036000 1295559 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": 842447, "vin": [ { "gen": { "height": 842437 } } ], "vout": [ { "amount": 992331036, "target": { "key": "a4a61d97dcce7122955eb8ca89aab1d5186a85e12797bc383abfc0ff0cb8babe" } } ], "extra": [ 1, 32, 72, 90, 165, 177, 40, 182, 14, 158, 105, 205, 51, 204, 41, 30, 142, 178, 213, 133, 24, 216, 222, 122, 10, 247, 111, 133, 235, 46, 248, 173, 104, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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