Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b578a7b72002069a043fc6be62bb4e5c8a5bd86adbdb935c7ac8d6d85b97448

Tx prefix hash: 018c221dd49ae3441a5672cd2637dbbb8e2aed18be67f95924db8cad26c07054
Tx public key: 05e3900e1c7a181c709464143a6cf9fa92b1ae2fbeb820863c0fbe7cd8a2040a
Timestamp: 1728974714 Timestamp [UCT]: 2024-10-15 06:45:14 Age [y:d:h:m:s]: 00:100:06:19:43
Block: 1131960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71625 RingCT/type: yes/0
Extra: 0105e3900e1c7a181c709464143a6cf9fa92b1ae2fbeb820863c0fbe7cd8a2040a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bbf067f2ad7133be9803c89c930f1c0dad3eaaafe1c76f5e576be13776f1950 0.600000000000 1614869 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": 1131970, "vin": [ { "gen": { "height": 1131960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bbf067f2ad7133be9803c89c930f1c0dad3eaaafe1c76f5e576be13776f1950" } } ], "extra": [ 1, 5, 227, 144, 14, 28, 122, 24, 28, 112, 148, 100, 20, 58, 108, 249, 250, 146, 177, 174, 47, 190, 184, 32, 134, 60, 15, 190, 124, 216, 162, 4, 10, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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