Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 555680034ac6f660d7f18c3d8f078f2c148d2f6b2f131d15836a0e3ccf0a9516

Tx prefix hash: b7e2f906f4ffa7be387e430b046034dd4be00d59a4b4d32ae155d5b23e706103
Tx public key: 052374d6fb61668ae1624afaffd54564fd69100a0f9c372e6ea17cc1a619910c
Timestamp: 1640664926 Timestamp [UCT]: 2021-12-28 04:15:26 Age [y:d:h:m:s]: 03:076:18:30:13
Block: 405063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 833647 RingCT/type: yes/0
Extra: 01052374d6fb61668ae1624afaffd54564fd69100a0f9c372e6ea17cc1a619910c021100000001edb0d4a3000000000000000000

1 output(s) for total of 27.916339762000 dcy

stealth address amount amount idx
00: 96bf7b09d73a68500fcf2ae5ff5fb957a1dce0ab3e9aaafa11760b63874de914 27.916339762000 805378 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": 405073, "vin": [ { "gen": { "height": 405063 } } ], "vout": [ { "amount": 27916339762, "target": { "key": "96bf7b09d73a68500fcf2ae5ff5fb957a1dce0ab3e9aaafa11760b63874de914" } } ], "extra": [ 1, 5, 35, 116, 214, 251, 97, 102, 138, 225, 98, 74, 250, 255, 213, 69, 100, 253, 105, 16, 10, 15, 156, 55, 46, 110, 161, 124, 193, 166, 25, 145, 12, 2, 17, 0, 0, 0, 1, 237, 176, 212, 163, 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