Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1aeb3c4f904d7884fff0128a7c8f28bf573a6396748acca7223457146e2b49

Tx prefix hash: 8dd6dd0533b60a02b8533f57c0a787cb2c3674a3f62d441d6d029ef29664a21a
Tx public key: 24d0e3de2828a828f29d27048112d8c170c1dee564d73b157f5d7ccd80968b42
Timestamp: 1728930116 Timestamp [UCT]: 2024-10-14 18:21:56 Age [y:d:h:m:s]: 00:214:08:26:00
Block: 1131594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153003 RingCT/type: yes/0
Extra: 0124d0e3de2828a828f29d27048112d8c170c1dee564d73b157f5d7ccd80968b4202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e10cbcf4aed44e5b649a57801862c494aa45f555fff4c5715dbdc1e4cc6e221b 0.600000000000 1614497 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": 1131604, "vin": [ { "gen": { "height": 1131594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e10cbcf4aed44e5b649a57801862c494aa45f555fff4c5715dbdc1e4cc6e221b" } } ], "extra": [ 1, 36, 208, 227, 222, 40, 40, 168, 40, 242, 157, 39, 4, 129, 18, 216, 193, 112, 193, 222, 229, 100, 215, 59, 21, 127, 93, 124, 205, 128, 150, 139, 66, 2, 17, 0, 0, 0, 6, 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