Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 774e757354ef545d4bd9bfc8252e1fe77cc61bb4e32fb15ef3e8b5605ed13838

Tx prefix hash: 82b4e58b3164822249ea924b70d950efa5025b58c7310c8a83477f667c6fafcc
Tx public key: a505d1e3befdc445bd6436850a5fd8c4fb35f00e2f46101c46693f0746333ad9
Timestamp: 1716098325 Timestamp [UCT]: 2024-05-19 05:58:45 Age [y:d:h:m:s]: 00:282:05:54:03
Block: 1025208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201708 RingCT/type: yes/0
Extra: 01a505d1e3befdc445bd6436850a5fd8c4fb35f00e2f46101c46693f0746333ad90211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f4b3a28f82c6c66b87157989d5d35399b02276843e52f326c62a7035a3738e1 0.600000000000 1491545 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": 1025218, "vin": [ { "gen": { "height": 1025208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f4b3a28f82c6c66b87157989d5d35399b02276843e52f326c62a7035a3738e1" } } ], "extra": [ 1, 165, 5, 209, 227, 190, 253, 196, 69, 189, 100, 54, 133, 10, 95, 216, 196, 251, 53, 240, 14, 47, 70, 16, 28, 70, 105, 63, 7, 70, 51, 58, 217, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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