Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9843755dde2b6fbe4ca4c1b0049c51375be50688385689c1015a2ebdec9fd12e

Tx prefix hash: 052d497bdaaaa0ffeb736bce8b5fe7f7049cf7c88d597a9aa42d232c27a03779
Tx public key: b171551236a08c932b0ca206b28a410ab4e5f8b442cb80e21e03891d0a2b2bf1
Timestamp: 1704109987 Timestamp [UCT]: 2024-01-01 11:53:07 Age [y:d:h:m:s]: 01:010:03:56:01
Block: 925811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268592 RingCT/type: yes/0
Extra: 01b171551236a08c932b0ca206b28a410ab4e5f8b442cb80e21e03891d0a2b2bf102110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db30676686f1b6b04ecba2a81d3f3f5cc002fbfef7d512f077d52f1e71610ebb 0.600000000000 1383581 of 15

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": 925821, "vin": [ { "gen": { "height": 925811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db30676686f1b6b04ecba2a81d3f3f5cc002fbfef7d512f077d52f1e71610ebb" } } ], "extra": [ 1, 177, 113, 85, 18, 54, 160, 140, 147, 43, 12, 162, 6, 178, 138, 65, 10, 180, 229, 248, 180, 66, 203, 128, 226, 30, 3, 137, 29, 10, 43, 43, 241, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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