Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f00524b37319e90996a07f08f5988a864a331b8b0a260b6307d3a6e15e821d

Tx prefix hash: 0d8958c66940c68d047fe40f56230d254ea0a1c99515133a109dfbe08c066cc8
Tx public key: b123ac6c7b5cf36e72d8257033257da567273b48cf11fb55cdfe013613432d15
Timestamp: 1700889495 Timestamp [UCT]: 2023-11-25 05:18:15 Age [y:d:h:m:s]: 01:351:12:04:17
Block: 899119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510103 RingCT/type: yes/0
Extra: 01b123ac6c7b5cf36e72d8257033257da567273b48cf11fb55cdfe013613432d15021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.643940137000 dcy

stealth address amount amount idx
00: 2810b0f71e38fcd883e512cb2c80c85adc97c9abdefea2c519dd45f33aea6408 0.643940137000 1355562 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": 899129, "vin": [ { "gen": { "height": 899119 } } ], "vout": [ { "amount": 643940137, "target": { "key": "2810b0f71e38fcd883e512cb2c80c85adc97c9abdefea2c519dd45f33aea6408" } } ], "extra": [ 1, 177, 35, 172, 108, 123, 92, 243, 110, 114, 216, 37, 112, 51, 37, 125, 165, 103, 39, 59, 72, 207, 17, 251, 85, 205, 254, 1, 54, 19, 67, 45, 21, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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