Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f09907391410fbf5377fdbe825e5caea123fe40a96a7c2ac97eccda8abb766f

Tx prefix hash: 0264c85f54d4bca5c472b4ccfa00acaf89b2be9501fd6bd5ab70df6e80e2a0a5
Tx public key: 1f837587d2c5fe2eafd1301123c61e55a017d252559b8bde5fdaadfa569779b3
Timestamp: 1701822168 Timestamp [UCT]: 2023-12-06 00:22:48 Age [y:d:h:m:s]: 01:109:14:07:47
Block: 906849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339468 RingCT/type: yes/0
Extra: 011f837587d2c5fe2eafd1301123c61e55a017d252559b8bde5fdaadfa569779b3021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.607061633000 dcy

stealth address amount amount idx
00: b0295de05c1e787da93e8669ccf63564ad2633cd39d9047c11018d2925591ce7 0.607061633000 1363808 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": 906859, "vin": [ { "gen": { "height": 906849 } } ], "vout": [ { "amount": 607061633, "target": { "key": "b0295de05c1e787da93e8669ccf63564ad2633cd39d9047c11018d2925591ce7" } } ], "extra": [ 1, 31, 131, 117, 135, 210, 197, 254, 46, 175, 209, 48, 17, 35, 198, 30, 85, 160, 23, 210, 82, 85, 155, 139, 222, 95, 218, 173, 250, 86, 151, 121, 179, 2, 17, 0, 0, 0, 7, 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