Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7e1e192a4e757fe589d60e5c907cfe44610560c46d270c49c8fedb36cca0784

Tx prefix hash: d95d472f517839daeb86cf9b7591cf71466f2d6d1d2a710a255378e00260188b
Tx public key: fd7238f76e1383690b9ad8ce74401811e9d49941c1b4f89bf3c373cd6fcb9d21
Timestamp: 1729360925 Timestamp [UCT]: 2024-10-19 18:02:05 Age [y:d:h:m:s]: 00:018:22:30:06
Block: 1135154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13486 RingCT/type: yes/0
Extra: 01fd7238f76e1383690b9ad8ce74401811e9d49941c1b4f89bf3c373cd6fcb9d2102110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65a541ea2399b883582c180dff941e936495499c2b9f66f08d78f7b1ca2fb628 0.600000000000 1618485 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": 1135164, "vin": [ { "gen": { "height": 1135154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65a541ea2399b883582c180dff941e936495499c2b9f66f08d78f7b1ca2fb628" } } ], "extra": [ 1, 253, 114, 56, 247, 110, 19, 131, 105, 11, 154, 216, 206, 116, 64, 24, 17, 233, 212, 153, 65, 193, 180, 248, 155, 243, 195, 115, 205, 111, 203, 157, 33, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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