Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc1b0bae5af38c2449661cee551cd88dda4bc00189575f933df46b9807cad402

Tx prefix hash: 532a81326bca503f81c43627ae551159999b0a9b2955d5aa15623d69f39708d7
Tx public key: 3e02d61ed1a4abfba1a5aded4091c469b73c476895f960293ca1e4c5c779c325
Timestamp: 1583539046 Timestamp [UCT]: 2020-03-06 23:57:26 Age [y:d:h:m:s]: 05:245:04:26:59
Block: 77924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1328030 RingCT/type: yes/0
Extra: 013e02d61ed1a4abfba1a5aded4091c469b73c476895f960293ca1e4c5c779c3250211000000278a2ee0d9000000000000000000

1 output(s) for total of 338.693009609000 dcy

stealth address amount amount idx
00: 4a0d3f9273765f9cbbbe39e4732e797ed3c014ecedb7652a92616e0f1de0fbd8 338.693009609000 143169 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": 77934, "vin": [ { "gen": { "height": 77924 } } ], "vout": [ { "amount": 338693009609, "target": { "key": "4a0d3f9273765f9cbbbe39e4732e797ed3c014ecedb7652a92616e0f1de0fbd8" } } ], "extra": [ 1, 62, 2, 214, 30, 209, 164, 171, 251, 161, 165, 173, 237, 64, 145, 196, 105, 183, 60, 71, 104, 149, 249, 96, 41, 60, 161, 228, 197, 199, 121, 195, 37, 2, 17, 0, 0, 0, 39, 138, 46, 224, 217, 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