Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99d9a3b89bf3febcc0ab5642151371bb6d5cfaa72f6c1cfbc1652746a758fb22

Tx prefix hash: 6e6534bf5b418298002d5e1e934fe074e1c6288d6eb30611931ccc2959631a3c
Tx public key: 04403d7ccabfe0012887f0a5c038b6ebbb5b309050b013ba9e847420b63c7fd5
Timestamp: 1617578102 Timestamp [UCT]: 2021-04-04 23:15:02 Age [y:d:h:m:s]: 03:267:14:16:44
Block: 233351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 950971 RingCT/type: yes/0
Extra: 0104403d7ccabfe0012887f0a5c038b6ebbb5b309050b013ba9e847420b63c7fd50211000000304405d762000000000000000000

1 output(s) for total of 103.469379602000 dcy

stealth address amount amount idx
00: aa5afd4f74889b5d41873e89a493cae7e0a7fc9edf960925be3bf2f0cd3aa2e5 103.469379602000 484615 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": 233361, "vin": [ { "gen": { "height": 233351 } } ], "vout": [ { "amount": 103469379602, "target": { "key": "aa5afd4f74889b5d41873e89a493cae7e0a7fc9edf960925be3bf2f0cd3aa2e5" } } ], "extra": [ 1, 4, 64, 61, 124, 202, 191, 224, 1, 40, 135, 240, 165, 192, 56, 182, 235, 187, 91, 48, 144, 80, 176, 19, 186, 158, 132, 116, 32, 182, 60, 127, 213, 2, 17, 0, 0, 0, 48, 68, 5, 215, 98, 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