Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 521dd8d1175d7556719f84e94952f536c2598b3cc1b0b8fc21549fab145c96f3

Tx prefix hash: 3cd67405748bdb8bcc267d8c30fa620e121b1cff43a24e18b8bcb49a261d083b
Tx public key: 400511247d2fb17d4796ca2bffc1d0a95bf3071203672ce99b94a93a1581f364
Timestamp: 1580262300 Timestamp [UCT]: 2020-01-29 01:45:00 Age [y:d:h:m:s]: 05:033:03:17:47
Block: 54213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175360 RingCT/type: yes/0
Extra: 01400511247d2fb17d4796ca2bffc1d0a95bf3071203672ce99b94a93a1581f364021100000001391a8d0e000000000000000000

1 output(s) for total of 405.866228447000 dcy

stealth address amount amount idx
00: 6274f09fd8228711faf0faaf7a227a729295a3fd43082adc954350323f836612 405.866228447000 100517 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": 54223, "vin": [ { "gen": { "height": 54213 } } ], "vout": [ { "amount": 405866228447, "target": { "key": "6274f09fd8228711faf0faaf7a227a729295a3fd43082adc954350323f836612" } } ], "extra": [ 1, 64, 5, 17, 36, 125, 47, 177, 125, 71, 150, 202, 43, 255, 193, 208, 169, 91, 243, 7, 18, 3, 103, 44, 233, 155, 148, 169, 58, 21, 129, 243, 100, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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