Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 300f97f6365f8ac132763c7ce0a86c6f6d73d9c0a1a6b165e3af64ec4f474ad9

Tx prefix hash: 6aa6027931c18abbec1807dff5257146de2a539f69e1310c92948ff1b0d59f6b
Tx public key: 975a5bd6cecd8afe29f2186aec4c78040759a10349a4a4bb6f64ef8974d15ec3
Timestamp: 1711587367 Timestamp [UCT]: 2024-03-28 00:56:07 Age [y:d:h:m:s]: 01:226:05:25:14
Block: 987830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420351 RingCT/type: yes/0
Extra: 01975a5bd6cecd8afe29f2186aec4c78040759a10349a4a4bb6f64ef8974d15ec302110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50f5f79c648915f155e4eba36b60185c364633b9e1ffd7108ec0172f909f539c 0.600000000000 1448089 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": 987840, "vin": [ { "gen": { "height": 987830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50f5f79c648915f155e4eba36b60185c364633b9e1ffd7108ec0172f909f539c" } } ], "extra": [ 1, 151, 90, 91, 214, 206, 205, 138, 254, 41, 242, 24, 106, 236, 76, 120, 4, 7, 89, 161, 3, 73, 164, 164, 187, 111, 100, 239, 137, 116, 209, 94, 195, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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