Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d534ee301e68b5a690aac6a7eb2e6215d359289dcc9c4564842ebe3bcf0ea8c

Tx prefix hash: d72dede7e1b2e484a5ab999d39c58b287035cb735b4b5e3c0d8d18c8c5a4d837
Tx public key: f94803938cafacb02091232ab1b9db572756cac8e2af6f642443cdbc6e99e036
Timestamp: 1706483406 Timestamp [UCT]: 2024-01-28 23:10:06 Age [y:d:h:m:s]: 00:301:10:44:28
Block: 945474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215852 RingCT/type: yes/0
Extra: 01f94803938cafacb02091232ab1b9db572756cac8e2af6f642443cdbc6e99e0360211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b288e09af376a6bb4a1a8781349aa9fa1928bdc4cb2189799bc282d8f94ea1b9 0.600000000000 1403788 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": 945484, "vin": [ { "gen": { "height": 945474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b288e09af376a6bb4a1a8781349aa9fa1928bdc4cb2189799bc282d8f94ea1b9" } } ], "extra": [ 1, 249, 72, 3, 147, 140, 175, 172, 176, 32, 145, 35, 42, 177, 185, 219, 87, 39, 86, 202, 200, 226, 175, 111, 100, 36, 67, 205, 188, 110, 153, 224, 54, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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