Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cb4892d2244d18c58d80a6b33832bf4120cfb5c862f7a0267bb50f44a729fdf

Tx prefix hash: ed1080a55a8968058f4c5f1a290f84b492c34ea0e89da05e39535e37eb8a3836
Tx public key: aee855459192e87e9d2363c5cd2017a1c9266155ee24f5100e830524a941637f
Timestamp: 1704893456 Timestamp [UCT]: 2024-01-10 13:30:56 Age [y:d:h:m:s]: 01:099:18:41:49
Block: 932309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332419 RingCT/type: yes/0
Extra: 01aee855459192e87e9d2363c5cd2017a1c9266155ee24f5100e830524a941637f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f7e1d87b0e8b69dc4daae5d94b7b0d1a1453fd0e0d20e84bd1734b48466fb46 0.600000000000 1390241 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": 932319, "vin": [ { "gen": { "height": 932309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f7e1d87b0e8b69dc4daae5d94b7b0d1a1453fd0e0d20e84bd1734b48466fb46" } } ], "extra": [ 1, 174, 232, 85, 69, 145, 146, 232, 126, 157, 35, 99, 197, 205, 32, 23, 161, 201, 38, 97, 85, 238, 36, 245, 16, 14, 131, 5, 36, 169, 65, 99, 127, 2, 17, 0, 0, 0, 6, 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