Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47e0d5bb65e0fd13f00f47b77ef779d890c3165e1347bcdd6d3f996b24b2279

Tx prefix hash: 619ad456fe3d4b202b50345c4fd55f0c6465cd234794e224120591c9bbc11adf
Tx public key: 2e4ca581ae771d8f2e1a772e31b811eca9068d5bda85ce60c2f1f39e9fcf5662
Timestamp: 1714353883 Timestamp [UCT]: 2024-04-29 01:24:43 Age [y:d:h:m:s]: 00:240:15:18:25
Block: 1010741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172259 RingCT/type: yes/0
Extra: 012e4ca581ae771d8f2e1a772e31b811eca9068d5bda85ce60c2f1f39e9fcf566202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f662862200432f9c0ed767ba9ceb56a6213d12d02fd81456d337a4dd269a5381 0.600000000000 1472783 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": 1010751, "vin": [ { "gen": { "height": 1010741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f662862200432f9c0ed767ba9ceb56a6213d12d02fd81456d337a4dd269a5381" } } ], "extra": [ 1, 46, 76, 165, 129, 174, 119, 29, 143, 46, 26, 119, 46, 49, 184, 17, 236, 169, 6, 141, 91, 218, 133, 206, 96, 194, 241, 243, 158, 159, 207, 86, 98, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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