Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1165430cb1544707acff7274b4cb6175bf1930f54a92699195ee58b4ec6df33d

Tx prefix hash: fc943e920d4366b240c82be696ec1cb2c42c591a35e9066f268ad6afe25d7fc8
Tx public key: 36b808b858c3238b3c3bc3b1067e2af5ed5c658994afee04d2f25d8e4468144e
Timestamp: 1727989085 Timestamp [UCT]: 2024-10-03 20:58:05 Age [y:d:h:m:s]: 00:110:08:03:25
Block: 1123796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78830 RingCT/type: yes/0
Extra: 0136b808b858c3238b3c3bc3b1067e2af5ed5c658994afee04d2f25d8e4468144e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60c5c9f89a381acf1defa1236e029f5be5707a26cff224aedc3eca9ba9953c00 0.600000000000 1606331 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": 1123806, "vin": [ { "gen": { "height": 1123796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60c5c9f89a381acf1defa1236e029f5be5707a26cff224aedc3eca9ba9953c00" } } ], "extra": [ 1, 54, 184, 8, 184, 88, 195, 35, 139, 60, 59, 195, 177, 6, 126, 42, 245, 237, 92, 101, 137, 148, 175, 238, 4, 210, 242, 93, 142, 68, 104, 20, 78, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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