Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe9c067f28c1d6edeaa08fd88b87f1ad691b6334bc0f8278357658eedcb4ca0

Tx prefix hash: 53818b6e4a1a2a7cd837348193cf7c13b7325ff16861214b1c18cc52ac3400fa
Tx public key: ee57131bef715d6f5de0541d4503bba4ddbf4df09e9b47ad18f731f2864564e2
Timestamp: 1726663417 Timestamp [UCT]: 2024-09-18 12:43:37 Age [y:d:h:m:s]: 00:112:19:49:40
Block: 1112794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80678 RingCT/type: yes/0
Extra: 01ee57131bef715d6f5de0541d4503bba4ddbf4df09e9b47ad18f731f2864564e2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb8f9376d29fba82dbfdd7f0dbc4309609fb6895d1145bceef3f5a8edb169f1d 0.600000000000 1592241 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": 1112804, "vin": [ { "gen": { "height": 1112794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb8f9376d29fba82dbfdd7f0dbc4309609fb6895d1145bceef3f5a8edb169f1d" } } ], "extra": [ 1, 238, 87, 19, 27, 239, 113, 93, 111, 93, 224, 84, 29, 69, 3, 187, 164, 221, 191, 77, 240, 158, 155, 71, 173, 24, 247, 49, 242, 134, 69, 100, 226, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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