Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d8813cfab9537fb19a95799d10579ea475ec7ee7cb2a1c0c26017a2a77cfa8e

Tx prefix hash: ed0909881010b65bc4c88a29481b35ada4e2e58f6866af7a294f16b34d543da6
Tx public key: 547fd7214bcb42b35b1e46bcc0974078c0de7c49e0458cb44d843998ae7c3dbe
Timestamp: 1677471554 Timestamp [UCT]: 2023-02-27 04:19:14 Age [y:d:h:m:s]: 01:262:08:45:15
Block: 705859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448402 RingCT/type: yes/0
Extra: 01547fd7214bcb42b35b1e46bcc0974078c0de7c49e0458cb44d843998ae7c3dbe02110000000283600029000000000000000000

1 output(s) for total of 2.813170287000 dcy

stealth address amount amount idx
00: 6eb0165e1c33593818645702e5eb522c02eaade5924410f7457206b4633235e2 2.813170287000 1149572 of 0

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": 705869, "vin": [ { "gen": { "height": 705859 } } ], "vout": [ { "amount": 2813170287, "target": { "key": "6eb0165e1c33593818645702e5eb522c02eaade5924410f7457206b4633235e2" } } ], "extra": [ 1, 84, 127, 215, 33, 75, 203, 66, 179, 91, 30, 70, 188, 192, 151, 64, 120, 192, 222, 124, 73, 224, 69, 140, 180, 77, 132, 57, 152, 174, 124, 61, 190, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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