Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11fb82b7f51125011dced302054aae4edbe16e787b4545168f0166702d8605b6

Tx prefix hash: 4fdf6e68402d2d8d5d52a20541e1f9600431cc7fcba8c83eb68c4d4c5a26b34c
Tx public key: 8fd2503aabfce6dc95a3e360e156b293dcc9f87bd2a7f4246c5c3efb41793776
Timestamp: 1711530033 Timestamp [UCT]: 2024-03-27 09:00:33 Age [y:d:h:m:s]: 00:293:18:02:55
Block: 987359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210246 RingCT/type: yes/0
Extra: 018fd2503aabfce6dc95a3e360e156b293dcc9f87bd2a7f4246c5c3efb417937760211000000020011055b000000000000000000

1 output(s) for total of 0.600080000000 dcy

stealth address amount amount idx
00: f344bbf9491da4ba8482e7090ccd24b0b441a5dd94216ee4b7b2cfc9f10982ab 0.600080000000 1447606 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": 987369, "vin": [ { "gen": { "height": 987359 } } ], "vout": [ { "amount": 600080000, "target": { "key": "f344bbf9491da4ba8482e7090ccd24b0b441a5dd94216ee4b7b2cfc9f10982ab" } } ], "extra": [ 1, 143, 210, 80, 58, 171, 252, 230, 220, 149, 163, 227, 96, 225, 86, 178, 147, 220, 201, 248, 123, 210, 167, 244, 36, 108, 92, 62, 251, 65, 121, 55, 118, 2, 17, 0, 0, 0, 2, 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