Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856ab5b16eef790e559a9aadce5cf705a00fb2e78291a807e1aa042d1da50e88

Tx prefix hash: 4eb7925d4215c4928f60cc76a2b989f1dffe69102cb0f7afc4596e8bfcade823
Tx public key: e4a90d0a3f5976d2bc751b1e7bcc7f621f3510c1640d87219924086296aef0c7
Timestamp: 1635348849 Timestamp [UCT]: 2021-10-27 15:34:09 Age [y:d:h:m:s]: 03:024:02:06:05
Block: 361637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 795632 RingCT/type: yes/0
Extra: 01e4a90d0a3f5976d2bc751b1e7bcc7f621f3510c1640d87219924086296aef0c702110000000ca272b9cb000000000000000000

1 output(s) for total of 38.881848423000 dcy

stealth address amount amount idx
00: 1d36dd23a4299b4241fcf49ce95ca918e17073223ea4dc131a6d3f71ac884ab2 38.881848423000 735671 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": 361647, "vin": [ { "gen": { "height": 361637 } } ], "vout": [ { "amount": 38881848423, "target": { "key": "1d36dd23a4299b4241fcf49ce95ca918e17073223ea4dc131a6d3f71ac884ab2" } } ], "extra": [ 1, 228, 169, 13, 10, 63, 89, 118, 210, 188, 117, 27, 30, 123, 204, 127, 98, 31, 53, 16, 193, 100, 13, 135, 33, 153, 36, 8, 98, 150, 174, 240, 199, 2, 17, 0, 0, 0, 12, 162, 114, 185, 203, 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