Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59ba0b0e3bb782cc00cb92133ebb2835c1b5ee1a8f5a6fb38055a97a41be80f1

Tx prefix hash: 0d3fc18467799d852abbf1a1c443ea59c2394fa8e10ece00c531bce56b2400af
Tx public key: d2e02818cffa0d6340a22ee10e69643f89079ec20c8b8be533cd69dbe367727b
Timestamp: 1732731476 Timestamp [UCT]: 2024-11-27 18:17:56 Age [y:d:h:m:s]: 00:107:20:29:07
Block: 1163013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76897 RingCT/type: yes/0
Extra: 01d2e02818cffa0d6340a22ee10e69643f89079ec20c8b8be533cd69dbe367727b0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49df0f81f7cf346874ae819c3ac132cfaed3a4f86d90cd3f8f52dfb60e39a54c 0.600000000000 1648676 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": 1163023, "vin": [ { "gen": { "height": 1163013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49df0f81f7cf346874ae819c3ac132cfaed3a4f86d90cd3f8f52dfb60e39a54c" } } ], "extra": [ 1, 210, 224, 40, 24, 207, 250, 13, 99, 64, 162, 46, 225, 14, 105, 100, 63, 137, 7, 158, 194, 12, 139, 139, 229, 51, 205, 105, 219, 227, 103, 114, 123, 2, 17, 0, 0, 0, 7, 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