Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 548c98e73e297c1cbd393014eb24748f2a5c6054166d9890cd7ad242b2e0ed79

Tx prefix hash: 4a64fc1a3e50eb6036d87dbffe03145d2bfafe7b6edafd52c20d854e2fbab99d
Tx public key: 24b69f40b5e731410fb11eba50cc2e912adf89effe0d1ad6fdb8a220c1537467
Timestamp: 1717301948 Timestamp [UCT]: 2024-06-02 04:19:08 Age [y:d:h:m:s]: 01:014:01:44:30
Block: 1035193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270859 RingCT/type: yes/0
Extra: 0124b69f40b5e731410fb11eba50cc2e912adf89effe0d1ad6fdb8a220c153746702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d56b90ca1aa5718a771fed6fdf9f8c63a32e59ec36c5a0e9607da5a9dde32e 0.600000000000 1503712 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": 1035203, "vin": [ { "gen": { "height": 1035193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d56b90ca1aa5718a771fed6fdf9f8c63a32e59ec36c5a0e9607da5a9dde32e" } } ], "extra": [ 1, 36, 182, 159, 64, 181, 231, 49, 65, 15, 177, 30, 186, 80, 204, 46, 145, 42, 223, 137, 239, 254, 13, 26, 214, 253, 184, 162, 32, 193, 83, 116, 103, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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