Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f097e9a5d130934cde4a55a4a0221ccefa6734360372c47ca4bdef9e9cc9b3b0

Tx prefix hash: 8f9489b15db63c89bcca6881c6a1084224ab462f8439f68182ccf688a3886f09
Tx public key: bb5a5452e7490bba27ecf0aa3fb0f267797fcf4838a79ce78fc1b7f9aaa165b0
Timestamp: 1719411245 Timestamp [UCT]: 2024-06-26 14:14:05 Age [y:d:h:m:s]: 00:263:21:02:54
Block: 1052667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188571 RingCT/type: yes/0
Extra: 01bb5a5452e7490bba27ecf0aa3fb0f267797fcf4838a79ce78fc1b7f9aaa165b00211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d959c3c6fdaa98b1795c7312d71fc6bd9239920edd848f5ca9b0aecd98d4d1b9 0.600000000000 1522998 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": 1052677, "vin": [ { "gen": { "height": 1052667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d959c3c6fdaa98b1795c7312d71fc6bd9239920edd848f5ca9b0aecd98d4d1b9" } } ], "extra": [ 1, 187, 90, 84, 82, 231, 73, 11, 186, 39, 236, 240, 170, 63, 176, 242, 103, 121, 127, 207, 72, 56, 167, 156, 231, 143, 193, 183, 249, 170, 161, 101, 176, 2, 17, 0, 0, 0, 1, 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