Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccdfb9c349fa36a965cc0cff661a3556f0bdf923ae253ccba48d7ba11b195a6a

Tx prefix hash: 359b2fc41a610a6dc9fd14b12bfc454ea9bc206451034947a5e3a78a39840de8
Tx public key: 58bc52b5703d9cdb4285aba56a66a6655ca4d202dbce407346dfd295b3027c21
Timestamp: 1730919253 Timestamp [UCT]: 2024-11-06 18:54:13 Age [y:d:h:m:s]: 00:077:06:33:47
Block: 1147999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55239 RingCT/type: yes/0
Extra: 0158bc52b5703d9cdb4285aba56a66a6655ca4d202dbce407346dfd295b3027c2102110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7259e9aa902013c1a4fc630a78bbc9a745efcaa1d520ca9926c80969a8b898e 0.600000000000 1632730 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": 1148009, "vin": [ { "gen": { "height": 1147999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7259e9aa902013c1a4fc630a78bbc9a745efcaa1d520ca9926c80969a8b898e" } } ], "extra": [ 1, 88, 188, 82, 181, 112, 61, 156, 219, 66, 133, 171, 165, 106, 102, 166, 101, 92, 164, 210, 2, 219, 206, 64, 115, 70, 223, 210, 149, 179, 2, 124, 33, 2, 17, 0, 0, 0, 15, 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