Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e53f5469566e9cfbaa11599cbe78ae900772f1d8212e015af4210ff7292be62

Tx prefix hash: f965373c6d815ec380f710f2994ac135495d5d211421e22a66bd0aaf23d3bdce
Tx public key: c650896c2c6406be9e9a9fcf3af8a24f13f92437c1335a520624b2a71aeca9aa
Timestamp: 1704297057 Timestamp [UCT]: 2024-01-03 15:50:57 Age [y:d:h:m:s]: 01:171:23:26:37
Block: 927387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383814 RingCT/type: yes/0
Extra: 01c650896c2c6406be9e9a9fcf3af8a24f13f92437c1335a520624b2a71aeca9aa021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a920fffb8943ded99361c3521e691a560fa15a4a188f21ad4bcf095f66fc3fd 0.600000000000 1385223 of 15

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": 927397, "vin": [ { "gen": { "height": 927387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a920fffb8943ded99361c3521e691a560fa15a4a188f21ad4bcf095f66fc3fd" } } ], "extra": [ 1, 198, 80, 137, 108, 44, 100, 6, 190, 158, 154, 159, 207, 58, 248, 162, 79, 19, 249, 36, 55, 193, 51, 90, 82, 6, 36, 178, 167, 26, 236, 169, 170, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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