Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6dbd7e1b6fefa893e70398daa5ce77218331e4df82597f55af845650bc16e8c

Tx prefix hash: b64ab82c2feb332657a8424e3a3170a74cae149a3fd84ef57673796c3f86a5a3
Tx public key: 39f26ea929d99c1d239dbf1884cebc272063c1d2e59b2e55a94de10810475654
Timestamp: 1732114558 Timestamp [UCT]: 2024-11-20 14:55:58 Age [y:d:h:m:s]: 00:130:11:32:52
Block: 1157896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93066 RingCT/type: yes/0
Extra: 0139f26ea929d99c1d239dbf1884cebc272063c1d2e59b2e55a94de108104756540211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f627a9f95491590b8a58a537cf3e2917c14b4c71fb65be62d326ad0f17569a2 0.600000000000 1643519 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": 1157906, "vin": [ { "gen": { "height": 1157896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f627a9f95491590b8a58a537cf3e2917c14b4c71fb65be62d326ad0f17569a2" } } ], "extra": [ 1, 57, 242, 110, 169, 41, 217, 156, 29, 35, 157, 191, 24, 132, 206, 188, 39, 32, 99, 193, 210, 229, 155, 46, 85, 169, 77, 225, 8, 16, 71, 86, 84, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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