Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fde0aa36e57479ca64da67117993450206b748924739882ec4a46a3a46d791f2

Tx prefix hash: 669a4f3dee86aaae92538b0fad1d63b152dc0b39190bae0fb79db4923f7d678a
Tx public key: 91a2a2feabaa70a04603509c1e89bf60b3b54998a77adabe1829a2fa5a58362d
Timestamp: 1705304266 Timestamp [UCT]: 2024-01-15 07:37:46 Age [y:d:h:m:s]: 01:070:23:00:41
Block: 935701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311800 RingCT/type: yes/0
Extra: 0191a2a2feabaa70a04603509c1e89bf60b3b54998a77adabe1829a2fa5a58362d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 699e30e2e5039dc8cbb8dd6de077a47485fdd8c2fb9050b33fad39d311d6f70f 0.600000000000 1393717 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": 935711, "vin": [ { "gen": { "height": 935701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "699e30e2e5039dc8cbb8dd6de077a47485fdd8c2fb9050b33fad39d311d6f70f" } } ], "extra": [ 1, 145, 162, 162, 254, 171, 170, 112, 160, 70, 3, 80, 156, 30, 137, 191, 96, 179, 181, 73, 152, 167, 122, 218, 190, 24, 41, 162, 250, 90, 88, 54, 45, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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