Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6015f5d4881e52c4169917a30c37e2be3e8ba9ba3cbc08236825240650cd3ba

Tx prefix hash: 53efa8d26a4fb6b957ca55330be54dc1f63edccbc4dfc1b90407d65b29246cbf
Tx public key: 7f04e8dbe84358f392d8313dcf2e37d1e9d0e6818241126d2a733a291b5949fa
Timestamp: 1594714838 Timestamp [UCT]: 2020-07-14 08:20:38 Age [y:d:h:m:s]: 04:223:02:50:38
Block: 117569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106449 RingCT/type: yes/0
Extra: 017f04e8dbe84358f392d8313dcf2e37d1e9d0e6818241126d2a733a291b5949fa0211000001c655fb4ae5000000000000000000

1 output(s) for total of 250.291346524000 dcy

stealth address amount amount idx
00: f52712bdca8c14b3286f3ae3577c48e452ab6f9a1ee1276af420d78ca3b25dc6 250.291346524000 200819 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": 117579, "vin": [ { "gen": { "height": 117569 } } ], "vout": [ { "amount": 250291346524, "target": { "key": "f52712bdca8c14b3286f3ae3577c48e452ab6f9a1ee1276af420d78ca3b25dc6" } } ], "extra": [ 1, 127, 4, 232, 219, 232, 67, 88, 243, 146, 216, 49, 61, 207, 46, 55, 209, 233, 208, 230, 129, 130, 65, 18, 109, 42, 115, 58, 41, 27, 89, 73, 250, 2, 17, 0, 0, 1, 198, 85, 251, 74, 229, 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