Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea418d9111f1060dc2913d43639fdfe08022679e39b994b3c1529da3d5ef78cf

Tx prefix hash: 5611dee45cda129aefd5807d8bd0f019c033b35a014f6a20685b8ecde573ab30
Tx public key: cb4d71a6cc381b75aa484a3f09b5dbd19ea9269c98bbc17e4f76ab01e147caf1
Timestamp: 1715643870 Timestamp [UCT]: 2024-05-13 23:44:30 Age [y:d:h:m:s]: 01:179:01:55:17
Block: 1021439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386600 RingCT/type: yes/0
Extra: 01cb4d71a6cc381b75aa484a3f09b5dbd19ea9269c98bbc17e4f76ab01e147caf10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2230bd0249ed50505cfafa42fd40a2a173f84927a2b548c436001d856f487c3d 0.600000000000 1485760 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": 1021449, "vin": [ { "gen": { "height": 1021439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2230bd0249ed50505cfafa42fd40a2a173f84927a2b548c436001d856f487c3d" } } ], "extra": [ 1, 203, 77, 113, 166, 204, 56, 27, 117, 170, 72, 74, 63, 9, 181, 219, 209, 158, 169, 38, 156, 152, 187, 193, 126, 79, 118, 171, 1, 225, 71, 202, 241, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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