Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243ceafda3685faf281c20a1d118a6ad4f5aebb5d6c76bd443f16f886fb09e7b

Tx prefix hash: 33c7669ff5de35971ed1d9ec59f89ac29e630dde6ff20c8874159fa3d9812543
Tx public key: e7efd6f4ccb3d036e5a67a912d6e478487de2361ee7019c78d9ca9f2332af3fe
Timestamp: 1737961880 Timestamp [UCT]: 2025-01-27 07:11:20 Age [y:d:h:m:s]: 00:141:20:15:34
Block: 1206084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101299 RingCT/type: yes/0
Extra: 01e7efd6f4ccb3d036e5a67a912d6e478487de2361ee7019c78d9ca9f2332af3fe0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8991b1ab0218dbc2afbdbec336a7e39c1ba80f4f0c04fe3c454b61de16af78 0.600000000000 1692785 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": 1206094, "vin": [ { "gen": { "height": 1206084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8991b1ab0218dbc2afbdbec336a7e39c1ba80f4f0c04fe3c454b61de16af78" } } ], "extra": [ 1, 231, 239, 214, 244, 204, 179, 208, 54, 229, 166, 122, 145, 45, 110, 71, 132, 135, 222, 35, 97, 238, 112, 25, 199, 141, 156, 169, 242, 51, 42, 243, 254, 2, 17, 0, 0, 0, 2, 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