Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87eae4b66102f6672fea9ea6cec613d29fa501cce9c02258c63709aa22da365e

Tx prefix hash: 3bc1abe85d4d0d92ddf1ac416f160ccc74f53b13ffa2b1b57bd47d96eaae45de
Tx public key: d97b54f77cb1e82d7347ebb5f5b5eb1ec9bbd374d8ac69698ccff4196c916917
Timestamp: 1728002083 Timestamp [UCT]: 2024-10-04 00:34:43 Age [y:d:h:m:s]: 00:231:22:53:16
Block: 1123905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165601 RingCT/type: yes/0
Extra: 01d97b54f77cb1e82d7347ebb5f5b5eb1ec9bbd374d8ac69698ccff4196c91691702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c535284111ccf5e303886d481c35f923103d2e5aeb971c8e3a0ef7bde87e7f6c 0.600000000000 1606454 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": 1123915, "vin": [ { "gen": { "height": 1123905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c535284111ccf5e303886d481c35f923103d2e5aeb971c8e3a0ef7bde87e7f6c" } } ], "extra": [ 1, 217, 123, 84, 247, 124, 177, 232, 45, 115, 71, 235, 181, 245, 181, 235, 30, 201, 187, 211, 116, 216, 172, 105, 105, 140, 207, 244, 25, 108, 145, 105, 23, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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